Bump reconverse to 58921e9 (#217, #222); grow the reconverse CI tier; skip classic-only tests on reconverse - #3974

…ic-only tests

Reconverse main 58921e9 carries two fixes found by Charm++'s own tests:

- #217: CmiWithinNodeBroadcast now follows the classic delivery contract:
  nokeep messages shared by reference, a zerocopy broadcast receive
  delivered to the calling PE only, the caller's buffer consumed. Before it,
  tests/charm++/within_node_bcast aborted at +pe 2 and six of the nine
  tests/charm++/zerocopy directories segfaulted at +pe 4.
- #222: reconverse declares CMK_ONESIDED_IMPL (and CMK_ONESIDED_RO_DISABLE),
  so zcQdIncrement creates one quiescence count per Direct-API RDMA
  operation, matching the single acknowledgement of reconverse's RMA path.
  Before it, zerocopy_with_qd with two processes never reached quiescence
  after its Direct API test. It also declares CMK_MACHINE_PROGRESS_DEFINED,
  so CkNetworkProgress() now drives the network instead of compiling to
  nothing.

reconverse-ci's TEST_DIRS gains within_node_bcast and eight zerocopy
directories, the tests that caught both bugs; zerocopy/zc_post_modify_size
stays out until reconverse #223 (a two-process data mismatch present before
and after these fixes) is resolved.

tests/charm++/queue and tests/charm++/longIdle are filtered out of TESTDIRS
under reconverse (CMK_GDIR=reconverse): queue tests classic's Cqs API,
which the reconverse build does not compile, and longIdle needs
CcdCallOnConditionOnPE, which reconverse lacks. tests/converse/megacon is
likewise skipped: it is written against the Cpm interface; reconverse
carries its own port of the bank (tests/megarecon, reconverse PR #218).

Verified on macOS arm64 with the equivalent tree (#217 + #222 as the
submodule): the whole TEST_DIRS tier passes in one and two processes,
zerocopy_with_qd included; nine of nine zerocopy directories pass single
process, eight with two processes. An Anvil run (two nodes, InfiniBand,
hwloc) is in progress and gates the merge.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Charm's feature detection turned CMK_USE_CMA on for every Linux build with
process_vm_readv, reconverse included. Reconverse has no CMA transport:
its conv-rdma.cpp compiles the CMA paths only under a CMK_USE_CMA it never
defines, and it does not parse +noCMAForZC. So a reconverse-linux build
compiled dead CMA branches into Charm++, and the zerocopy tests' Makefiles,
which run their +noCMAForZC variants when CMK_USE_CMA is 1, handed the flag
to programs that do not consume it: "Usage: ./zerocopy_with_qd <array
size>" on Linux CI, while the same tier passes on macOS where CMK_HAS_CMA
is 0. Found by the first Linux run of the widened reconverse-ci tier.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>